-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[SVLS-7025] improve AAS documentation #30014
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SVLS-7025] improve AAS documentation #30014
Conversation
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Created DOCS-11280 for documentation team review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved with a few comments and suggestions.
content/en/serverless/azure_app_services/azure_app_services_container.md
Outdated
Show resolved
Hide resolved
|
||
#### Using the Datadog CLI | ||
|
||
First, install the [Datadog CLI][601] and [Azure CLI][602]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the other tabs on the page use numbered steps but this one doesn't. I don't think it's crucial, but just pointing out it's a little inconsistent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, this is intentional since once they have the dependencies installed, there is only one step: running the CLI.
The simplicity is primarily why we are offering the new method
…ntainer.md Co-authored-by: Michael Cretzman <[email protected]>
What does this PR do? What is the motivation?
Improves the AAS documentation to be more clear about how to get set up with Datadog Azure App Services Monitoring:
installing the Datadog Azure Integration and AAS instrumentation.
Also includes the automated setup which is now GA in the Datadog CLI
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>
convention and include the forward slash (/
). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes